Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use -pack switch instead of -allconfigurations to create packages #110778

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Dec 17, 2024

We don't do incremental servicing in runtime anymore and hence don't need to rely on the GeneratePackageOnBuild property. Use the -pack action (which implies building all TFMs) instead of -allconfigurations (which implied also creating packages).

I need to queue an official build to test this E2E.

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 17, 2024
Copy link
Member

@jkoritzinsky jkoritzinsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once we have a test official build.

@@ -64,7 +64,7 @@ extends:
- windows_x64
jobParameters:
templatePath: 'templates-official'
buildArgs: -s tools+libs -allConfigurations -c $(_BuildConfig) /p:TestAssemblies=false /p:TestPackages=true
buildArgs: -s tools+libs -allConfigurations -c $(_BuildConfig) /p:BuildAllConfigurations=true /p:TestAssemblies=false /p:TestPackages=true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why don't we pass -pack here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because libraries packages shouldn't be generated for libraries packages in runtimelab: https://github.com/dotnet/runtime/blame/e65457031da52f57d03da721f381a82a5be64c03/eng/packaging.targets#L31

@@ -28,7 +27,6 @@ stages:
# Stages-based publishing entry point
- template: /eng/common/templates-official/post-build/post-build.yml
parameters:
publishingInfraVersion: ${{ parameters.publishingInfraVersion }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unrelated change?

Copy link
Member Author

@ViktorHofer ViktorHofer Dec 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. The publishing infra version doesn't need to be set anymore. We removed the explicit set from most other repos. I didn't want to open a separate PR just for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants